
APAR= II10202
AS/400 CLIENT ACCESS FOR WINDOWS 95/NT DATA TRANSFER INFORMATION


** Last updated 3/4/97 **


Use Client Access Data Transfer instead of PC5250 File Transfer
---------------------------------------------------------------
The File Transfer option on the PC5250 toolbar requires a PRPQ
to be installed on the AS/400.  This PRPQ is purchased
separately.  The PRPQ File Transfer enables users to upload and
download entire files.  A more powerful and recommended option
is to use the Client Access Data Transfer.

Client Access Data Transfer can be found in the Client Access
folder or invoked via a wizard by right-clicking your mouse
over an empty area, selecting New, and then selecting:

o Data Transfer From AS/400
o Data Transfer To AS/400

The Client Access Data Transfer can also be placed on the PC5250
toolbar by doing the following:

1. Open a PC5250 Display session
2. Click the right-mouse button on the toolbar and select
   "Create Item..."
3. Click on the Application tab.
4. Type the application name as:
   C:Progra 1IBMClient 1CWBTF.EXE
   Note:  characters should be replaced with backslashes.
5. Type the application parameters as:
    /t
6. Click on the Visual button.  This sets what you are shown
   on the toolbar.
7. Type AS400->PC at the Toolbar text field
8. Type a description such as Data Transfer From AS/400
9. Click on OK.  An item for invoking Data Transfer From AS/400
   will be added to your toolbar.

To add 'Data Transfer To AS/400' replace step 5 with an /f.
You will also want to change the text type in at steps 7 and 8
to reflect a Data Transfer-To-AS/400 request.

After you have added Data Transfer to the PC5250 toolbar, you
may want to remove the PC5250 File Transfer options to avoid
confusion.  Follow these steps to delete the file transfer
items:

1. Click the right-mouse button on the Send item on the toolbar.
2. Select Delete Item
3. Repeat these steps for the Receive button on the toolbar.

After you have completed your toolbar customization, you must
save the toolbar.  To do this, follow these steps:

1. Click the right mouse button on the toolbar and select
   "Save..."
2. Type the name you wish to save the file as and click on the
   Save button.

You can also remove the PC5250 File Transfer menu items by using
the Menu-Bar Customization Utility icon in the Client Access
Accessories folder.
Reference: Lotus Notes doc #5751509

Current limitations with Data Transfer
--------------------------------------

o  DDM Files -  Data Transfer does not provide access to DDM
   files on the AS/400 or their associated data.  Ref: SA57156.

o  S36 "database" files - Data Transfer does not provide acces
   to data residing in IDDU linked S36 files.  Ref: SA57157.

o  Downloads with left outer joins - Data Transfer does not
   currently handle requests involving multiple file join
   requests when the 'Return records with missing fields
   checkbox' is selected.  When this checkbox is selected,
   Data Transfer attempts to do a left outer join of the
   files.  This function has been reported as not working
   correctly; a solution is being investigated.  Inner joins
   of multiple files work fine.  Reference: SA58487 & SA61019.

o  CCSID 65535 data conversion - Data transfer does not
   translate data between ASCII and EBCDIC if the CCSID of the
   file or fields on the AS/400 is 65535.  A fix for this is
   available in the current PTFs available for the Windows 95
   client (V3R1M0 and V3R1M1 levels).  If you do not have the
   PTF fix code on your PC, the following may occur:

   --Uploads to the AS/400 file will generate message CWBTF0005
     "Data in this field is incorrect or does not match PC data
     type."

   --Downloads to the PC will complete successfully, but the
     data will not be converted, appearing as hex data instead
     of the expected character data.

   With the PTF fix code, Data Transfer will allow conversion
   from CCSID 65535 to the PC CCSID on transfers to the PC.
   The AS/400 job CCSID is used for the conversion.  Data
   Transfer also converts from the PC CCSID to the AS/400 job
   CCSID for transfers to the AS/400 when fields are tagged
   with the 65535 CCSID.

   This conversion is controlled by creating an INI file named
   CWBTFR.INI in the directory Windows was installed to.  The
   .INI file must contain the section heading and a
   ForceTranslation line.

    o  Sample for translation of 65535 data:
       (In the following sample, < and > should be replaced
        with square brackets)

               <Client Access Data Transfer>
               ForceTranslation=1;

    o  Sample for no translation of 65535 data:
       (In the following sample, < and > should be replaced
        with square brackets)

               <Client Access Data Transfer>
               ForceTranslation=0;

    If the .INI file is not found, or the correct section and
    value names are not present, Client Access Data Transfer
    will default to no translation of 65535 data.

    WARNING: Enable this fix only if you are confident the data
    contained within columns tagged with the 65535 CCSID are in
    a defined CCSID that matches the user profile CCSID of the
    jobs that will access it.  Accessing 65535 CCSID data from a
    job CCSID that does not match the data may corrupt data
    within the database file.  If you don't enable this fix by
    providing a CWBTFR.INI file, transfers will continue to
    behave as they did before before applying this PTF.

    Columns tagged with the 65535 CCSID are designed to not be
    converted when transferring to/from the PC.  Using this
    fix, which forces a conversion to take place, is to be done
    only when it is not possible to change the column or file
    CCSID from 65535.  Every attempt should be made to
    appropriately tag the data with the correct CCSID.

    For more information on the 65535 CCSID, see topic 2.2.3.2
    in the AS/400 National Language Support Book (SC41-3101-00).

    Conversions from CCSID 65535 fields are error-prone under
    multi-language situations where AS/400 user-job CCSIDs do
    not match.

    Reference: SA55521.  See the PTF cover letter or
    the Client Access service pack readme file for
    further information.

o  Data Transfer MUST run in subsystem QSERVER
   - Novell SAA and Microsoft SNA server users should
     reference apar SA56403.
   - See apar SA57453 for all connectivity types.

o  A full listing of the differences between Data Transfer
   and Client Access File Transfer is available to
   supportline customers via lotus notes doc #5673322.


"Unable to Start Database Server" error
---------------------------------------
   See II09599 for information on debugging the
   database server program.
